Deloitte partnered with Zespri to create conceptual designs new portal, in this 10 weeks long engagement, we facilitated Design Sprints to co-design the portal with Zespri SMEs to create build ready designs that could be handed over to Zespri’s development partner.
The case study focuses will be geo and design sprints.
We delivered over 450 screens and 200 stories in a short time frame, the digital map experience cutting 70% of the time for kiwifruit growers to complete compliance. For conceptual design validation, we whipped up lo-fi designs to test future features with our growing community in focus group workshops. teaming up with Zespri to lock down what would be designed and delivered for Day 1. Every design sprint was hands-on—we ran in-person co-design workshops to dig into growers' behaviors, gather requirements, validate early concepts, and make sure the designs clicked with business goals, with a sharp focus on integrating geospatial capability. Stakeholder collaboration was all about regular check-ins and technical chats to stay aligned and keep feedback flowing for fast, high-quality iterations. We backed up front-end development by documenting UI components, states, layouts, and complex geospatial interactions, all following best practices to deliver accessible, multi-device designs. For the detailed designs, we synced with BAs to nail user stories and crafted polished solutions that worked seamlessly across devices.
it was uncovered that there is a need for digitals to be provided to better support the Kiwifruit community in making on- orchard decisions, as well as meeting Zespri compliance requirements. Based off this initial research, Deloitte was engaged to support Zespri over 10 weeks to support them to validate concepts for the portal, define this into a MVP product, and then produce build ready designs.
The current system is spread across different modules, leading to a disconnected experience for growers, that also means a complex and high learning curve, and double handlings. Our solution focuses on pulling all key operations for spray workflows together, the records flow seamlessly to risk management, pest monitoring, and compliance tracking. This approach save heaps of time for growers and spray contractors and help them get on top of their tasks. Zespri compliance requires growers to highlight risks, which is currently done using physical maps. We are integrating new geospatial capabilities using Azure Maps out-of-the-box features, growers can interact with paperless map experience, visualising temporal data in heat maps, drawing lines or areas directly on the map to indicate risks, this enables more site feature reusability, accurate data capturing and reviewing which are critical for meeting compliance and long-term efficiency, accessing map views and feature can be done with a single click from table views.
The lack of an integrated geospatial solution forces farmers and contractors to rely on static paper maps and disconnected systems to manage compliance and operational tasks, such as rotary filing systems with years of records. Without a digital map, users also struggle to visualize orchard layouts, annotate hazards, or track spatial data like pest levels and spray coverage effectively. Let’s divide and conquer each challenge.
Paper map is unable to to alert graower if the pest level has exceeded, thhey wont to able to look into the details of any site features, Paper maps also fail to scale with the growing complexity of orchard layouts, fail to help grower visulise geospatial data Users
We digitise the map expereince entirely. use on any device: we pan / zoom / rotate, visulise the orchards that grower own, toggle differennt map layers to best help complete their day-to-day task, or like decision what map feature user wan to show. we use flyout to expand into future info on what user click without cluttering the main map integrface. It stays in sync with the latest pest moinrotinr and spray data to ensure the map we always up to date.
The a list of block name hard to differentiate as it lack showing promixity, size and kwiifruit varies Without a digital map, grower and contractor struggle to visually connect blocks of orchards to the job they need to carry out which leads to confusion and heaps of time waste when there can be hundreds of blocks involved.
map enablede efficiently and visually selecting the correct blocks for tasks like spraying: beyond that, adapt to different contexts or show additional layers of information (e.g., pest levels, hazards to info what and how to spray), making it difficult to make informed decisions. switching bewteen map and list works seamlessly in any workflow with single click.
Paper map doesn't meet the scaling needs for kiwifruit business and For zespri, auditing geosptial data is citical evaluation for kiwifruit orchard eligblity and compliance. Currently, Users rely on static paper maps to manually label hazards, chemical storage, and neighboring features on paper maps.. papers maps data cannot flow directly into risk mangement or reproting, cause alot of manual cross referencing, drawing can be messay quickly and the labour intensity makign it near impossiblty to be accurate for both grower and reviewrer.
biggest breakthrough is we enable people to draw areas or drop pins on map: This allows site features water source, chemnical storage need to be labled during spray and take procaution, to be future-proofing. by reduing the papper map msyness and ther resubity of all site features and tracking all geo hazards in the coming year, cut down 70% of time spend on map-related argichemical compliances.
With map, data flows bewteen differnet module from spray to risk assessmnet to continous imporvement to compliance tracking to stay in sync with lastest data and allow update , make complinace more accurate and confidence for both grwoers and zespri auditors.
Onboarding: the benifit for drawing on mapis clear, but how might we help user navigate this advanced map feature and mental shift? We strike a balance bewteen well informed and simplifed, and reference mainstream map drawing apps:
1. Simlify the complex: It's packed with feature, but Tha map view interaf look alot like google map that user fmiarl with, for new users, want offer in-app help on all clickables button on hover on to be more mentally prepared and not being intimated
2. Contextual tooltip: user will not feel left alone when they pickup a new tool or first use the map, they will be informate with protips on how they can create point or close the shapes when "Draw a shape" is picked up, or general intro to map opening the map view.
3. Cursor tooltip: While drawing show tooltip follows cursor as they draw shapes, to instrution and remind user the extact click or mouse movment they might need based on drawing progress, such "Select a starting point", "Click to add point", "Click to close shape" and more
~breathe~
We understand that design can be a time consuming process, and we only want to spend time and effort on things that we know are going to add value to our users. Therefore when designing net new experiences, we work quickly to generate concepts that are lo-fi, but have enough detail that we can take to market. r Zespri, in the span of three weeks we facilitated workshops to understand their aspirations for the future, potential features, and created a lo-fi experience of the portal which we took out to the Kiwifruit community for validation. Through this we were able to determine customer feasibility, and determine which features we should consider as part of MVP.
While we create conceptual designs, we created high-level user requirements in Jira to capture the essence of the feature we were doing. Once we'd determined what was desirable from a suer point of view, we then worked with Zespri to prioritise features to form Day 1 scope. This formed the basis of the MVP experience we took through to our 10 week Design Sprint..
Running design sprints is the only way we could deliver large-scale designs (450+ screens and 170+ user stories) and a fully-fledged design library from scratch within 5 sprints in the quality that cliet appreicate. Each sprint started with a board of thoughtful questions, reimagining the current state, wireframing, d planning card sorting and whiteboarding exercises with the dient in the next 3 days. We fly up to the Auckland office to run those workshop co faciltated by designer and BA fully dive into all features. We could then take notes for high-fidelity design and hold frequent check-ins to validate with different stakeholders within Zespri.
We also collobrate with non-delitte development team and with daily check-ins with them as well as make sure thei BA and Devs are unblocked (Design for mobile and tablet and taking design system up to date is a big one). As a design hygeine, we annotate our dseign with note and link them to exact reference user stories to improve clarity and reduce back andforot. This approach allowed us to thoroughly address complex problems we couldn't fully solve in a single sprint. We reviewed and reflected on the wider context as new feature needs arose, and planned improvements for the next sprint. As a result, we impressed client with the quality and value we provided at the end of the 10 weeks.
Testing is running in paralle with design sprint, it's a crtical part to take in feedback from outside voice and improve. REsearcher managed to carry out 3 rounds wiht design support during the sprint. We prioritsie the needs and wants swith zespri, and make effective changes such as adding help texts on each page, reduce the requirements to simpfliy workflows. The positive and confidence we get from customer testing lead up to frictionless final sign off from client
"It works for a lot of our individual clients and even new clients as well." - Accounting Partner